Designing with defaults

Roughly nine in ten users never change a default. That number should terrify and liberate you in equal measure: terrify, because your defaults are your product for most people; liberate, because it means you get to decide what good looks like.

Teams treat settings as generosity. More often they are abdication — every toggle is a decision the team could not make, shipped to someone with less context to make it instead.

Defaults are opinions

The best defaults encode a point of view. Ledger ships with plain-language balances because we believe hex strings are for auditors. Verse opens with suggestions collapsed because we believe the writer's cursor is sacred. Users can change both. Almost nobody does — not because they cannot find the switch, but because the opinion is right.

A practical test for any new setting: if you cannot say which value ninety percent of users should want, you have not finished designing. The setting is a question you are asking your users. Answer it yourself first.

Strong defaults, few settings, and the humility to change the default when the data disagrees — that is the whole discipline.